keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
× Questions about A400/800/1200 Analog Interface Card

Elastix Can't Send Caller ID to Client

13 years 8 months ago #5990 by lisa.gao
hi,
First you should confirm this:
which is the format of the caller id, dtmf or fsk?
If the format of caller id is dtmf ,you should set cidsignalling=dtmf;
If the format of caller id is fsk ,you should set cidsignalling=v23

13 years 8 months ago #5991 by james.zhu
hi:
please try:
cidsignalling=v23; if you are using fsk, or try bell
hideallerid=no
cidstart=polarity; try to set it to ring

13 years 8 months ago #5993 by michael880308
Hi
First of all, thanks for your helps, I tried to change the cidsignalling=v23 to dtmt, also the cidstart=polarity to ring, but none of them seems to work, this is what the asterisk log says when I made a call to Elastix after I made the changes and reboot it.
Aug 12 22:46:18 VERBOSE [3022] logger.c: -- Starting simple switch on 'DAHDI/1-1'
Aug 12 22:46:20 NOTICE [3022] chan_dahdi.c: Got event 17 (Polarity Reversal)...
Aug 12 22:46:20 NOTICE [3022] chan_dahdi.c: Got event 18 (Ring Begin)...
Aug 12 22:46:21 NOTICE [3022] chan_dahdi.c: Got event 2 (Ring/Answered)...
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@from-pstn:1] Set("DAHDI/1-1", "__FROM_DID=s") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@from-pstn:2] Gosub("DAHDI/1-1", "app-blacklist-check|s|1") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@app-blacklist-check:1] LookupBlacklist("DAHDI/1-1", "") in new stack
Aug 12 22:46:21 WARNING [3022] app_lookupblacklist.c: LookupBlacklist is deprecated. Please use ${BLACKLIST()} instead.
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@app-blacklist-check:2] GotoIf("DAHDI/1-1", "0?blacklisted") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@app-blacklist-check:3] Return("DAHDI/1-1", "") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@from-pstn:3] ExecIf("DAHDI/1-1", "1 |Set|CALLERID(name)=") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@from-pstn:4] Set("DAHDI/1-1", "__CALLINGPRES_SV=allowed_not_screened") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@from-pstn:5] SetCallerPres("DAHDI/1-1", "allowed_not_screened") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@from-pstn:6] Goto("DAHDI/1-1", "ivr-3|s|1") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Goto (ivr-3,s,1)
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@ivr-3:1] Set("DAHDI/1-1", "MSG=custom/MainWelcome") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@ivr-3:2] Set("DAHDI/1-1", "LOOPCOUNT=0") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@ivr-3:3] Set("DAHDI/1-1", "__DIR-CONTEXT=default") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@ivr-3:4] Set("DAHDI/1-1", "_IVR_CONTEXT_ivr-3=") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@ivr-3:5] Set("DAHDI/1-1", "_IVR_CONTEXT=ivr-3") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@ivr-3:6] GotoIf("DAHDI/1-1", "0?begin") in new stack
Aug 12 22:46:21 VERBOSE [3022] logger.c: -- Executing [s@ivr-3:7] Answer("DAHDI/1-1", "") in new stack
Aug 12 22:46:21 DEBUG [3022] chan_dahdi.c: Took DAHDI/1-1 off hook
This time, I didn't even see my phone number in the log, it seems like the setting polarity and v23 is right(Line 2 22:46:20), but it just can't passed to the client, any ideas?
Best regards
Michael Lu
13 years 8 months ago #5996 by lisa.gao
Please email me your SSH, I will check for you. And please add my MSN: This email address is being protected from spambots. You need JavaScript enabled to view it.

13 years 8 months ago #5997 by james.zhu
hi:
maybe you have to recompile the chan_dahdi.conf.

13 years 8 months ago #6011 by michael880308
Hi,
How can I recompile the chan_dahdi.conf after I did the changes(which command?).
I already reboot Elastix after I changed chan_dahdi.conf but it still the same!
Does anyone get the same problem as this one?
Best regards
Michael Lu
Time to create page: 0.044 seconds
Powered by Kunena Forum